AWS Systems Manager - Get Missing Patches for EC2 Instances for given Hostname

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Content Index

The playbook can be triggered manually from a Host Entity to get the missing patches on a managed EC2 instance. This playbook performs the following actions: 1. Get the Hostname from the Host Entity. 2. Get the Instance ID from AWS EC2 for given Hostname. 3. Get the missing patches for the Instance ID. 4. Add the missing patches to the incident comment.

Attribute	Value
Type	Playbook
Solution	AWS Systems Manager
Source	View on GitHub

Logic App Connectors

This playbook uses 2 Logic App connectors / built-in actions:

Connector / Action	Type	Connections	Actions
`azuresentinel`	Managed	1	1
`function`	Built-in	0	2

Action parameters (URLs, paths, function IDs)

`azuresentinel` (Managed)

Action	Method	Endpoint	Other
Add_comment_to_incident_(V3)	post	`/Incidents/Comment`	—

`function` (Built-in)

Action	Method	Endpoint	Other
DescribeInstancePatches	—	—	functionId=`[concat(variables('AWSSSMFuntionsAppId'), '/functions/DescribeInstancePatches')]`
GetInventory	—	—	functionId=`[concat(variables('AWSSSMFuntionsAppId'), '/functions/GetInventory')]`

Additional Documentation

📄 Source: AWSSystemsManagerPlaybooks/AWS-SSM-GetInstancePatches-HostEntityTrigger/readme.md

AWS-SSM-GetInstancePatches-HostEntityTrigger

Summary

The playbook can be triggered manually from a Host Entity to get the missing patches on a managed EC2 instance. This playbook performs the following actions:

Get the Hostname from the Host Entity.
Get the Instance ID of Managed EC2 instance for given Hostname.
Get the missing patches for the Instance ID.
Add the missing patches to the incident comment.

Prerequisites

Prior to the deployment of this playbook, AWS Systems Manager API Function App Connector needs to be deployed under the same subscription.
Refer to AWS Systems Manager API Function App Connector documentation to obtain AWS Access Key ID, Secret Access Key and Region.

Deployment instructions

To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
Fill in the required parameters:
- Playbook Name
- Functions App Name

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

Click the Microsoft Sentinel connection resource
Click edit API connection
Click Authorize
Sign in
Click Save
Repeat steps for other connections

b. Assign Playbook Microsoft Sentinel Responder Role

Select the Playbook (Logic App) resource
Click on Identity Blade
Choose System assigned tab
Click on Azure role assignments
Click on Add role assignments
Select Scope - Resource group
Select Subscription - where Playbook has been created
Select Resource group - where Playbook has been created
Select Role - Microsoft Sentinel Responder
Click Save

c. Function App Settings Update Instructions

Refer to AWS Systems Manager API Function App Connector documentation for Function App Application Settings (Access Key ID, Secret Access Key and Region) update instruction.

References